…tainerPendingState

Extends captureContainerPendingState so the driver-level state is fully
self-contained for blob reads as well. Attachment blob bytes are fetched and
added to snapshotBlobs keyed by storage ID, which ContainerStorageAdapter
already serves through its cache — no wire-format change required.

GC state is consulted when present: blobs GC has explicitly marked
unreferencedTimestampMs, tombstoned, or deleted are skipped. Blobs absent
from the GC graph are kept, since GC lag can leave recently-attached blobs
off the graph and dropping them would lose live data. When the snapshot has
no GC tree (GC disabled or pre-GC document), every attachment blob from the
BlobManager redirect table is included.

The relevant blob manager / GC constants and the minimal parsing logic are
duplicated locally to avoid a loader → runtime dependency; comments point
back to the canonical definitions in container-runtime and
runtime-definitions.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

…ware

Extends the driver-only capture to cover the whole referenced graph of the
container, not just attachment blobs.

- Honours ISnapshotTree.unreferenced: a shared tree walker skips any subtree
  flagged unreferenced by the summarizer (which sets the flag from GC state)
  and inlines contents of every other blob it reaches. Replaces the
  unfiltered getBlobContentsFromTree path.
- Pre-fetches loading-group snapshots: enumerates groupIds on the base
  snapshot (skipping unreferenced subtrees), fetches each via
  IDocumentStorageService.getSnapshot({ versionId, loadingGroupIds }), runs
  the fetched snapshot through the same tree walker, and serialises the
  result into IPendingContainerState.loadedGroupIdSnapshots. If the driver
  lacks getSnapshot support or no groupIds are declared, no groups are
  included.
- GC parsing is done once and shared between tree-level and attachment-blob
  filtering. captureReferencedAttachmentBlobs now takes pre-parsed GC data.

Renames captureAttachmentBlobs.ts to captureReferencedContents.ts to reflect
the broader scope.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Covers the reachability filtering and groupId-fetch paths that the local
end-to-end tests can't easily exercise (no summarizer runs in the local
test server, and TestFluidObjectFactory doesn't produce loading-group
datastores out of the box). Tests construct ISnapshotTree fixtures
directly and back readBlob/getSnapshot with an in-memory shim.

15 cases across readReferencedSnapshotBlobs, parseGcSnapshotData,
captureReferencedAttachmentBlobs, and captureGroupIdSnapshots — covering
unreferenced subtree skip, root .blobs special-casing, ISnapshot vs
ISnapshotTree input, GC lag tolerance (blobs absent from gcNodes are
kept), tombstone/deletedNodes skip, and groupId enumeration/dedup/fetch.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

…ptureFullContainerState

The function captures the whole referenced graph of the container (snapshot,
loading-group snapshots, inlined structural blobs, inlined attachment blobs,
trailing ops) — not just "pending state." The new name matches the scope.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

…e.spec

Collapse a multi-line chained .get() call onto a single line to satisfy
biome's formatter — CI was failing on `biome check .` in local-server-tests.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

…inerState

Four issues flagged by Copilot review on PR microsoft#27100:

1. captureFullContainerState created an IDocumentService but never called
   dispose(). Wrap the capture body in try/finally and dispose in the
   finally to release driver-held resources (sockets/caches).

2. readReferencedSnapshotBlobs fanned every blob read at every tree level
   into a single Promise.all, giving unbounded concurrency on large
   snapshots. Refactor into a collect-then-fetch pipeline: walk the tree
   synchronously to gather referenced blob ids, then fetch via a new
   mapWithConcurrency helper capped at 32 in-flight reads.

3. captureReferencedAttachmentBlobs had the same unbounded-parallel issue
   over all referenced attachment storage ids. Route through the same
   mapWithConcurrency helper.

4. collectUnreferencedBlobLocalIds returned undefined when gcData.gcState
   was undefined, silently dropping tombstones/deletedNodes filtering even
   when those lists were populated. Contradicted the function docs. Now
   always applies tombstones/deletedNodes regardless of gcState presence,
   and returns a (possibly empty) Set rather than undefined. Added a unit
   test covering the gcState-undefined-but-tombstones-present case.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Follow-up to 8a748cc: captureGroupIdSnapshots still fanned every
getSnapshot call into a single Promise.all. Route through
mapWithConcurrency with a lower limit (4) since each call pulls a whole
snapshot tree, not a single blob.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

…ip cache

Two issues from PR review:

1. Bind getSnapshot when extracting it from the storage service. Real
   driver implementations reference `this` (e.g.,
   LocalDocumentStorageService.getSnapshot reads this.id), so calling
   the detached method would TypeError in strict mode. Mirrors the
   bind pattern in protocolTreeDocumentStorageService.ts:31. Added a
   class-based unit test stub whose getSnapshot touches `this` — would
   have caught this.

2. Pass cacheSnapshot: false on every getSnapshot call we make from the
   capture path. This capture is transient; we don't want to pollute the
   driver's snapshot cache with it. Covered by a unit test asserting the
   option is forwarded.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

- Wire-format consts POJO + contract test
- GC-interesting test
- Monitoring context wired (to be reverted)
- API report regenerated